Date: Tue, 2 Aug 94 04:30:26 PDT From: Ham-Digital Mailing List and Newsgroup Errors-To: Ham-Digital-Errors@UCSD.Edu Reply-To: Ham-Digital@UCSD.Edu Precedence: Bulk Subject: Ham-Digital Digest V94 #258 To: Ham-Digital Ham-Digital Digest Tue, 2 Aug 94 Volume 94 : Issue 258 Today's Topics: Internet<>Packet (2 msgs) New New Packet Book Avail TAPR Bulletin: TAPR801.001 TRS-80 Model 100 (2 msgs) Welcome to rec.radio.info! Windows and Packet Radio Send Replies or notes for publication to: Send subscription requests to: Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Ham-Digital Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/ham-digital". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Sun, 31 Jul 1994 11:46:49 +0000 From: pipex!demon!imcldn.demon.co.uk!mike@uunet.uu.net Subject: Internet<>Packet To: ham-digital@ucsd.edu In article tmolloy@cix.compulink.co.uk "Tony Molloy" writes: > Are there any bridges between the Net and the Packet networks? It would > be useful to be able to e-mail to/from people who only quote packet > addresses. there are a couple, but unless you are licenced, you cannot use them Mike G7OBS -- ------------------------------------------------------------------------------- X400 : /RFC-822=mike(a)imcldn.demon.co.uk/O=mhs-relay/PRMD=uk.ac/ADMD= /C=GB/ ------------------------------------------------------------------------------- ------------------------------ Date: Mon, 1 Aug 1994 20:44:44 GMT From: ihnp4.ucsd.edu!agate!howland.reston.ans.net!pipex!lyra.csx.cam.ac.uk!doc.ic.ac.uk!uknet!cix.compulink.co.uk!tmolloy@network.ucsd.edu Subject: Internet<>Packet To: ham-digital@ucsd.edu Thanks. Couldn't it be handled like a phone-patch? Tony ------------------------------ Date: Mon, 1 Aug 94 02:07:00 -0500 From: ihnp4.ucsd.edu!agate!iat.holonet.net!wwswinc!barry.davis@network.ucsd.edu Subject: New To: ham-digital@ucsd.edu VBARNET BBS is now carrying this conference. --- Squish v1.01 * Origin: VBARNET * USA * (410)761-3406 or 922-8947 * PCB & OS/2 (1:261/1458) ------------------------------ Date: 2 Aug 1994 02:29:23 GMT From: ihnp4.ucsd.edu!agate!howland.reston.ans.net!europa.eng.gtefsd.com!news.uoregon.edu!gaia.ucs.orst.edu!news.CSOS.ORST.EDU!wagnerj@network.ucsd.edu Subject: New Packet Book Avail To: ham-digital@ucsd.edu Greetings - This is to let you know that a new book is available to packeteers. It is entitled "The Amateur Packet Radio Handbook" by Jim Wagner, KA7EHK. It is the first book I know about which really goes beyond the "how to buy a TNC and use a bbs" level. It discusses networking, TCP/IP, DX-spotting, KaNodes, Net/Rom, ROSE, TexNet, and much more. If you want a copy of the table of contents or an order form, please send a message to me at wagnerj.csos.orst.edu. Tnx and 73 de Jim Wagner ------------------------------ Date: 2 Aug 1994 00:14:21 GMT From: cs.utexas.edu!news.unt.edu!tcet.unt.edu!gjones@uunet.uu.net Subject: TAPR Bulletin: TAPR801.001 To: ham-digital@ucsd.edu SB TAPR @ TAPR $TAPR801.001 NEWS: TAPR to make available ARRL CNC and DC Proceedings Please use BID: $TAPR801.001 Tucson Amateur Packet Radio August 1st, 1994 ------------------------------------------------------------------------ TAPR to make available ARRL CNC and DC Proceedings ------------------------------------------------------------------------ TAPR has arranged an agreement with the ARRL to be the distribution point of past proceedings of the ARRL Computer Networking Conferences and Digital Conferences. This will apply to proceedings that are more than two years old. For example, the ARRL will continue to distribute the 12th (1993) and 13th (1994) proceedings this year, then next year TAPR will begin to distribute the 12th (1993). In this way, TAPR and the ARRL hopes that these proceedings will be fully available to digitally interested hams. Proceedings should be available from the TAPR office the end of August. TAPR would like the thank Mark Wilson, AA2Z, and Jon Bloom, KE3Z, for their help at the ARRL with this arrangement. --- There has been interest in having many of the papers available in electronic form. TAPR will begin to work on contacting authors for premission to generate computer versions of many of the papers. If you are an author of an ARRL CNC or DC proceedings paper and would like to give TAPR premission to make available your paper electronically, please send e-mail to tapr@tapr.org. If you have the paper in electronic form already, please send that also. More on this project as it forms. ------------------------------------------------------------------------ Tucson Amateur Packet Radio 8987-309 E Tanque Verde Rd #337 * Tucson, Az * 85749-9399 * 817-383-0000 JOIN TAPR! Be a part of the digital revolution! /EX ------------------------------ Date: 31 Jul 1994 17:30:19 -0700 From: nntp.crl.com!crl.crl.com!not-for-mail@decwrl.dec.com Subject: TRS-80 Model 100 To: ham-digital@ucsd.edu In the past I've seen the TRS-80 Model 100 used as a terminal for packet, and I'm curious about the software/code to do this. I think that the only language that this machine understands is BASIC, so where to find source code might be indicated. (Or was there a chip that handled this?) Comments, suggestions, etc.? TNX & 73 -- James Schumann, KE6DMY schumann@crl.com ------------------------------ Date: Mon, 1 Aug 1994 02:36:24 GMT From: netcomsv!netcom.com!fmitch@decwrl.dec.com Subject: TRS-80 Model 100 To: ham-digital@ucsd.edu James C. Schumann (schumann@crl.com) wrote: : In the past I've seen the TRS-80 Model 100 used as a terminal for packet, : and I'm curious about the software/code to do this. I think that the : only language that this machine understands is BASIC, so where to find : source code might be indicated. (Or was there a chip that handled this?) : Comments, suggestions, etc.? : TNX & 73 : -- the model 100 has a terminal program in rom... so you can use it with a tnc it works fine at modest baud rates (between the tnc and 100), but the display is a tad small... mitch wa4osr : James Schumann, KE6DMY : schumann@crl.com -- * * * I collect telegraph equipment (mostly bugs - Vibroplex) * * * ------------------------------------------------------------------------------- Email: fmitchell@rd.qms.com or, second choice, fmitch@netcom.com Felton "Mitch" Mitchell, WA4OSR, 11 Midtwon Park, E., Mobile, AL 36606 USA 205-342-7259 home, 205-476-4100 work, 205-476-0465 FAX co-sysop for W4IAX bbs running fbb ... sysop for WA4OSR DXCluster in Mobile.. ------------------------------------------------------------------------------ ------------------------------ Date: Sat, 30 Jul 1994 21:00:08 MDT From: ihnp4.ucsd.edu!agate!howland.reston.ans.net!gatech!newsxfer.itd.umich.edu!nntp.cs.ubc.ca!alberta!ve6mgs!rec-radio-info@network.ucsd.edu Subject: Welcome to rec.radio.info! To: ham-digital@ucsd.edu Archive-name: radio/rec-radio-info/welcome Last-modified: $Date: 1994/01/02 22:00 $ Version: $Revision: 1.06 $ *** Welcome to rec.radio.info! *** Welcome to rec.radio.info, a group that aims to provide a noise-free source of information and news for the entire rec.radio hierarchy. Two introductory articles about rec.radio.info are posted to the group and to news.answers every two weeks. You are now reading the first article, which explains what rec.radio.info is, and answers some Frequently Asked Questions. The second article is titled "Submission Guidelines", and you only need to read it if you want to submit an article to rec.radio.info. You can skip to the next section of this article by searching for the next " -- " string. The sections available are: - What is the purpose of rec.radio.info? - Why are messages almost always cross posted to rec.radio.info? - What is a 'follow-up', and what does 'moderated' mean? - OK, so now I know what 'moderated' means. Tell me more. - What type of material is considered inappropriate? - I do not have access to news, how can I get the information posted to rec.radio.info? - Will the material appearing in rec.radio.info be archived somewhere? - I have a regular posting with timely information, is there a way to speed up it's delivery, or automate for more convenience? -- What is the purpose of rec.radio.info? The purpose or charter of rec.radio.info is to provide the Usenet community with a resource for information, news, and facts about any and all things radio. All the other rec.radio groups are intended for discussions and general chit chat about radio. Rec.radio.info will contain informational, factual articles only. Follow-ups are redirected to an appropriate other group, and further discussion (if any) will not take place in rec.radio.info. In order to ensure that rec.radio.info contains only appropriate articles, it was decided to create the group as a moderated newsgroup. -- Why are messages almost always cross posted to rec.radio.info? It provides a "tag" for each article to be assembled into a filtered presentation in rec.radio.info (even with cross-posting, only one message, with a unique Message-ID, is propogated across the net). This tag also facilitates a pre-existing method of dropping or cancelling the articles locally within the discussion groups if you don't want to see them. This accommodates individuals who want to separate the bulletins from the discussions, discussions from the bulletins, as well as those who are adamant about not reading another newsgroup and wanted to see everything all in one basket. With the total size of Usenet (in number of newsgroups and total traffic) doubling every year or so, this is no insignificant contribution to reducing information noise and chaos. Making the discussion groups a catch-all, and making extra newsgroups filters on that catch-all, is also the most realistic way to implement such a scheme (It's not intuitively obvious what the charter, contents, and general appropriate topics for each and every newsgroup are. Seeing FAQ's and charter/intro postings in the home newsgroup is beneficial for new readers). By cross-posting one only is adding a few tens of bytes to each bulletin (to specify the extra group on the Newsgroups line), but are adding the capability for very powerful filtering features available on most news servers, listservers and readers. Your local news guru could probably explain these features in more detail. In rn, for example, according to Leanne Phillips in her rn kill-file FAQ, add a line of the form: /Newsgroups:.*[ ,]rec\.radio\.info/h:j either in ~/News/KILL (if you don't want to see rec.radio.info articles anywhere) or ~/News/rec/radio/amateur/misc/KILL (if you don't want to see them just in rec.radio.amateur.misc). The latter method means your kill file will only be consulted during rec.radio.amateur.misc (and hence runs more efficiently), and will probably work for most people. In nn, according to Bill Wohler in his nn FAQ, add a line of the form: rec.radio.info:!s/:^ in ~/.nn/kill (if you don't want to see rec.radio.info articles anywhere), or put the following lines: sequence rec.radio.info rec.radio. at the end of ~/.nn/init in order to see all the rec.radio.info bulletins first, then read the remaining rec.radio.* without the bulletins. -- What is a 'follow-up', and what does 'moderated' mean? If you are new to Usenet and are not familiar with the terminology, you might want to read the general introductory articles found in the newsgroup news.announce.newusers. Doing so will make your life on the net much easier, and will probably save you from making silly beginner's mistakes. If you think that at this moment you are reading an echo, a conference, or a bulletin board, I'd also strongly suggest a trip over to news.announce.newusers. For the rest of this article, I will assume you have a basic knowledge of Usenet terminology and mechanics. A moderated group means that any article that needs to be posted to the group has to be accepted by the moderator of the group. Since we need to ensure that followups to an article (discussion) do not show up in the rec.radio.info newsgroup, the `Followup-To:' header line contains a newsgroup that is appropriate for disussions about the specific article. -- OK, so now I know what 'moderated' means. Tell me more. Rec.radio.info is a moderated newsgroup, which means that all articles submitted to the group will have to be approved by the moderator first. The current moderator of the group is Mark Salyzyn. Submissions to rec.radio.info can be posted, or e-mailed to: rec-radio-info@ve6mgs.ampr.ab.ca Comments, criticisms, suggestions or questions about the group can be e-mailed to: rec-radio-request@ve6mgs.ampr.ab.ca But before you do so, please be sure to check out the "Submission Guidelines" article. The influence of the moderator should be minimal and of an administrative nature, consisting chiefly of weeding out obviously inappropriate articles, while making sure correct headers etc. are used for the appropriate ones. -- What type of material is considered inappropriate? There are three broad categories of articles which will be rejected by the moderator: 1) Requests for information: rec.radio.info is strictly a one-way street. I receive information in my mailbox; I then post it to rec.radio.info. Requests for specific information belong in the normal discussion newsgroups. If your request gets answered, you might consider passing the answer on to rec.radio.info, though. Especially if you can edit it into a informational, rather than a discussion, format. 2) Obvious discussion articles, or articles that appear unsubstantiated. 3) Commercial stuff: a relatively unbiased test of a radio product would be accepted, but any hint of for-profit might be reason for rejection. For three reasons: This is not the purpose of the list, for-profit is a controversial topic, and this list may be passed onto Amateur Packet Radio (where for-profit is prohibited except under certain provisos). rec.radio.swap (or possibly comp.newprod) may be more deserving of the posting in any matter. Similarly, copyrighted material generally cannot be used. If it's TRULY worthwhile to the net, I would recommend obtaining permission from the copyright holder. Please note the source, and if permission was given. I reserve the right to make the final decision concerning appropriateness in all situations. In most cases, a brief summary of, or pointer to, the copyrighted information may be all I can allow. -- I do not have access to news, how can I get the information posted to rec.radio.info? brian@UCSD.EDU (Brian Kantor) has kindly supplied a mail list server for rec.radio.info. Non of the articles will be digested, due to their size, so you will receive individual mailings for every article posted to the group. Mail sent to radio-info@ucsd.edu will be forwarded to the moderator and thus is an alias to rec-radio-info@ve6mgs.ampr.ab.ca To subscribe and unsubscribe via the listserver; the format for that is sub address radio-info unsub address radio-info where 'address' is your full mailing address. Send this request to listserv@ucsd.edu Note that the server will automatically delete any address that bounces mail. If you leave the address portion blank, it will try to deduce your address from the mail headers. This may not work if you are on bitnet, milnet or some other non-Unix host, so it is recommended to put your return address in any case. For example: sub mymailbox@myhost.mydomain.mil radio-info or sub MEMEME01@DMBHST.bitnet radio-info or something like that. -- Will the material appearing in rec.radio.info be archived somewhere? < Dated information here > Yes. Still firming up details at the moment but here is a preliminary list: - unbc.edu as maintained by Lyndon Nerenberg - nic.funet.fi maintained by Risto Kotalampi saved to /pub/dx/text/rec.radio.info currently stored as numbered files. Effectively this means that anything you post to rec.radio.info will be permanently stored, so your work will not be lost. -- I have a regular posting with timely information, is there a way to speed up it's delivery, or automate for more convenience? Yes, there is! It may take a bit of chatter with the moderator, but we are willing to take responsible people and provide them the means of posting the articles directly from their site. We will try everything we can as we fully realize that DX (distant signal) and astronomical data can be somewhat transitory. We are also willing to allow regular posters of information the same courtesy, even if the information is not as time critical. We refer to this as self-moderation, which is partly based on the model for news.answer. This requires co-operation and good will to be beneficial to the community in the rec.radio hierarchy. I suggest reading the posting guidelines for more information. I am open to suggestions. I thank the following individuals for their input into this article: rec.music.info moderator Leo Breebaart rec-music-info@cp.tn.tudelft.nl rec.radio.broadcasting moderator Bill Pfeiffer wdp@gagme.chi.il.us Paul W. Schleck, KD3FU pschleck@unomaha.edu Ian Kluft, KD6EUI ikluft@uts.amdahl.com -- Mark Salyzyn -- Moderator rec.radio.info Submissions to: rec-radio-info@ve6mgs.ampr.ab.ca Administrivia to: rec-radio-request@ve6mgs.ampr.ab.ca * Requests for information do *not* belong in rec.radio.info * ------------------------------ Date: 1 Aug 1994 18:55:02 GMT From: ihnp4.ucsd.edu!news.acns.nwu.edu!math.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!cleveland.Freenet.Edu!ei938@network.ucsd.edu Subject: Windows and Packet Radio To: ham-digital@ucsd.edu Packet Folks Two questions: 1. Does a packet modem driver for Win 3 exist for the Baycom modem? It occured to me this weekend that if Baycom can be used for TCPIP, then it could be used for TCPIP under Windows, right? 2. I checked out the BAYCOM15 program listed in archie searches... My German is not up to the task of figuring out what is going on with that program... Does an English version exist? It is the program that is written especially for the Baycom modem. Thanks!! Andrew Lynch alynch@wpgate1.wpafb.af.mil ------------------------------ End of Ham-Digital Digest V94 #258 ******************************